Input-output fabric conflict detection and resolution in a blade compute module system

ABSTRACT

Determining whether there exists an input-output (I/O) fabric conflict (mismatch) between a blade I/O fabric daughter card of a blade compute module and an I/O interface module of a blade compute module system, and if a conflicts does exit then taking action to correct this I/O fabric mismatch. An I/O fabric router may be coupled between the blade I/O fabric daughter cards and the system I/O interface modules. If a matching I/O interface fabric exists then the I/O fabric router will couple the blade I/O fabric daughter card to the matching I/O interface fabric. If there is no matching I/O interface fabric then the blade I/O fabric daughter card may be decoupled from the blade compute module system so that the associated blade compute module may otherwise function, and an alert may be sent regarding the I/O fabric conflict (absence of an I/O fabric match) for the I/O fabric daughter card of the blade compute module.

TECHNICAL FIELD

The present disclosure relates generally to information handling systemsand, more particularly, to input-output fabric conflict detection andresolution in a blade compute module system.

BACKGROUND

As the value and use of information continues to increase, individualsand businesses seek additional ways to process and store information.One option available to users are information handling systems. Aninformation handling system generally processes, compiles, stores,and/or communicates information or data for business, personal, or otherpurposes, thereby allowing users to take advantage of the value of theinformation. Because technology and information handling needs andrequirements vary between different users or applications, informationhandling systems may also vary regarding what information is handled,how the information is handled, how much information is processed,stored, or communicated, and how quickly and efficiently the informationmay be processed, stored, or communicated. The variations in informationhandling systems allow for information handling systems to be general orconfigured for a specific user or specific use such as financialtransaction processing, airline reservations, enterprise data storage,or global communications. In addition, information handling systems mayinclude a variety of hardware and software components that may beconfigured to process, store, and communicate information and mayinclude one or more computer systems, data storage systems, andnetworking systems, e.g., computer, personal computer workstation,portable computer, computer server, print server, network router,network hub, network switch, storage area network disk array, RAID disksystem and telecommunications switch.

As consumer demand increases for smaller and denser information handlingsystems, manufacturers strive to integrate more computer components intoa smaller space. This integration has led to the development of severalapplications, including high density compute modules. High densitycompute modules provide the computer processing resources of severalcomputers in a small amount of space. A typical arrangement for a highdensity compute module system includes a shared power supply system, amanagement module, shared input-output (I/O) interfaces, a connectionboard (e.g., a back-plane or mid-plane) and the compute modules.

Blade compute modules, or “blades,” are miniaturized compute modulesthat typically are powered from a common power supply system and arecooled by a cooling system within a multi-compute module cabinet.Typically, a blade includes a circuit board with one or more processors,memory, a connection port, and possibly a disk drive for storage. Byarranging a plurality of blades like books on a shelf in themulti-compute module cabinet, a high density multi-compute module systemachieves significant cost and space savings over a plurality ofconventional computers in separate enclosures. These savings resultdirectly from the sharing of common resources, e.g., I/O interfaces,power supplies, cooling systems, enclosures, etc., and the reduction ofspace required by this type of multi-compute module system whileproviding a significant increase in available computer processing power.

Blades may be adaptable for a number of different input-output (I/O)interface protocols in a multi-compute module information handlingsystem. Each of these I/O interface protocols may be interchanged to auser specified fabric, e.g., Ethernet network interface controller(NIC), Fibre Channel (FC), Infiniband, etc., by a modular daughter cardassociated with the respective blade, e.g., the modular daughter cardmay plug into a connector on the blade. Each daughter card connector isrouted to a specific I/O interface module. All of the daughter cardsconnected to the specific I/O interface module must have the same fabricas that I/O interface module for proper operation thereof. If a fabricmismatch between a daughter card and an I/O interface module occurs theblade is typically disabled. All variations of daughter cards share acommon mechanical form factor and also share a common electrical pin-outfor interfacing to the compute module system. Because of the similarmechanical form factor and common electrical pin-out of the differentmodular daughter cards, it is not uncommon for a fabric mismatch tooccur when a wrong daughter card is plugged into a connector (e.g., cardsocket) on the blade. In addition, even if the daughter cards connectedto the blade have the correct fabrics, they can still be populated,e.g., plugged into, the wrong daughter card sockets, i.e., the daughtercards have been swapped. Installation of an incorrect daughter card orincorrect swapping of otherwise correct daughter cards will result inthe blade being disabled and thereby becoming non-functional.

SUMMARY

What is needed and desired is a way of detecting a fabric mismatchbetween a modular daughter card of a blade compute module and an I/Ointerface module of an information handling system, and takingcorrective action so that the blade compute module may maintain fullfunctionality in the information handling system.

According to a specific example embodiment of this disclosure, aninformation handing system having input-output fabric conflict detectionand resolution may comprise a chassis management controller; at leastone input-output (I/O) interface; an I/O fabric router; and at least oneblade compute module having at least one I/O daughter card and a blademanagement controller; wherein the at least one I/O daughter card iscoupled to the I/O fabric router, the I/O fabric router is coupled tothe at least one I/O interface fabric, the blade management controlleris coupled to the at least one I/O daughter card, the I/O fabric routerand the chassis management controller, and the chassis managementcontroller is coupled to the at least one I/O interface; whereby theblade management controller determines the at least one I/O daughtercard fabric and reports the at least one I/O daughter card fabric to thechassis management controller, the chassis management controllerdetermines whether the at least one I/O interface fabric and the atleast one I/O daughter card fabric match or do not match, if the atleast one I/O interface fabric and the at least one I/O daughter cardfabric match then the information handling system boots up, if the atleast one I/O interface fabric and the at least one I/O daughter cardfabric do not match then the chassis management controller instructs theblade management controller to change the I/O fabric routing through theI/O fabric router so that the at least one I/O interface fabric and theat least one I/O daughter card fabric match, or will disable the atleast one I/O daughter card if there is no possible I/O fabric match forthe at least one I/O daughter card.

According to another specific example embodiment of this disclosure, aninformation handing system having input-output fabric conflict detectionand resolution may comprise a chassis management controller; at leastone input-output (I/O) interface; an I/O fabric router; and at least oneblade compute module having at least one I/O daughter card and a blademanagement controller; wherein the at least one I/O daughter card iscoupled to the I/O fabric router, the I/O fabric router is coupled tothe at least one I/O interface fabric, the blade management controlleris coupled to the at least one I/O daughter card, the I/O fabric routerand the chassis management controller, and the chassis managementcontroller is coupled to the at least one I/O interface; whereby thechassis management controller determines the at least one I/O interfacefabric and reports the fabric to the blade management controller, theblade management controller determines the at least one I/O daughtercard fabric and then determines whether the at least one I/O interfacefabric and the at least one I/O daughter card fabric match or do notmatch, if the at least one I/O interface fabric and the at least one I/Odaughter card fabric match then the information handling system bootsup, if the at least one I/O interface fabric and the at least one I/Odaughter card fabric do not match then the blade management controllerchanges the I/O fabric routing through the I/O fabric router so that theat least one I/O interface fabric and the at least one I/O daughter cardfabric match, or will disable the at least one I/O daughter card ifthere is no possible I/O fabric match for the at least one I/O daughtercard.

According to yet another specific example embodiment of this disclosure,a method for detecting input-output fabric conflicts and resolving anydetected fabric conflicts in an information handling system may comprisethe steps of: determining input-output (I/O) fabric types of a pluralityof I/O interfaces in an information handling system; determining I/Ofabric types of a plurality of I/O daughter cards associated with aplurality of blade compute modules; coupling each I/O fabric type of theplurality of I/O daughter cards to an associated one of the plurality ofI/O interfaces having the same I/O fabric type; and decoupling any oneof the I/O daughter cards having an I/O fabric type not found in any oneof the plurality of I/O interfaces.

According to still another specific example embodiment of thisdisclosure, a method for detecting input-output fabric conflicts andresolving any detected fabric conflicts in an information handlingsystem may comprise the steps of: initiating power-up of an informationhandling system comprising a plurality of blade compute modules and aplurality of input-output (I/O) interfaces; detecting I/O fabric typesof a plurality of I/O daughter cards associated with the plurality ofblade compute modules; detecting I/O fabric types of the plurality ofI/O interfaces; determining whether there are any I/O fabric conflictswith how the I/O fabrics of the plurality of I/O daughter cards arecoupled to the I/O fabrics of the plurality of I/O interfaces, whereinif there are no I/O fabric conflicts then sending a power-upconfirmation to a blade management controller of each of the pluralityof blade compute modules, enabling each of the I/O daughter cards, andcontinuing booting up the information handling system; if there is anI/O fabric conflict then determining if the I/O fabric conflict can beresolved, if the I/O fabric conflict can be resolved then swappingfabric connections to resolve the I/O fabric conflict, and if the I/Ofabric conflict cannot be resolved then sending a power-up denial to theblade management controller of the one of the plurality of blade computemodules having the I/O fabric conflict and disabling the one of theplurality of blade compute modules having the I/O fabric conflict.

BRIEF DESCRIPTION OF THE DRAWINGS

A more complete understanding of the present disclosure thereof may beacquired by referring to the following description taken in conjunctionwith the accompanying drawings wherein:

FIG. 1 is a schematic perspective view of a high density informationhandling blade compute module system, according to a specific exampleembodiment of the present disclosure;

FIG. 2 is a schematic block diagram of an information handling bladecompute module system, according to a specific example embodiment of thepresent disclosure;

FIG. 3 is a schematic block diagram of a more detailed input-output(I/O) fabric topology of the information handling blade compute modulesystem illustrated in FIG. 2, according to a specific example embodimentof the present disclosure; and

FIG. 4 is a flow diagram of a sequence of steps for checkinginput-output (I/O) fabric topology in a blade compute module system andfor taking corrective action when an I/O fabric topology conflictexists, according to a specific example embodiment of the presentdisclosure.

While the present disclosure is susceptible to various modifications andalternative forms, specific example embodiments thereof have been shownin the drawings and are herein described in detail. It should beunderstood, however, that the description herein of specific exampleembodiments is not intended to limit the disclosure to the particularforms disclosed herein, but on the contrary, this disclosure is to coverall modifications and equivalents as defined by the appended claims.

DETAILED DESCRIPTION

For purposes of this disclosure, an information handling system mayinclude any instrumentality or aggregate of instrumentalities operableto compute, classify, process, transmit, receive, retrieve, originate,switch, store, display, manifest, detect, record, reproduce, handle, orutilize any form of information, intelligence, or data for business,scientific, control, or other purposes. For example, an informationhandling system may be a personal computer, a network storage device, orany other suitable device and may vary in size, shape, performance,functionality, and price. The information handling system may includerandom access memory (RAM), one or more processing resources such as acentral processing unit (CPU), hardware or software control logic, readonly memory (ROM), and/or other types of nonvolatile memory. Additionalcomponents of the information handling system may include one or moredisk drives, one or more network ports for communicating with externaldevices as well as various input and output (I/O) devices, such as akeyboard, a mouse, and a video display. The information handling systemmay also include one or more buses operable to transmit communicationsbetween the various hardware components.

Referring now to the drawings, the details of specific exampleembodiments are schematically illustrated. Like elements in the drawingswill be represented by like numbers, and similar elements will berepresented by like numbers with a different lower case letter suffix.

Referring to FIG. 1, depicted is a schematic perspective view of a highdensity information handling blade compute module system, according to aspecific example embodiment of the present disclosure. The informationhandling blade compute module system, generally represented by thenumeral 200, comprises at least one blade compute module (BCM) 210, apower distribution board (PDB) 202, at least one power supply unit (PSU)206, at least one input-output (I/O) interfaces 284 and 286, a chassismanagement controller (CMC) 204, and an I/O fabric router 268. Incertain embodiments, one example of an information handling bladecompute module system 200 includes a high density blade compute modulesystem 200 that may form a part of a component rack system (notexpressly shown). Typically, the high density blade compute modulesystem 200 may include an enclosure or chassis 208 in which the at leastone PSU 206, I/O interfaces 284 and 286, CMC 204, PDB 202 and the atleast one BCM 210 may be enclosed therein. Each BCM 210 may include ablade management controller (BMC) 212 (see FIG. 2).

Although FIG. 1 depicts a mid-plane PDB 202 as being placed between CMC204 and the at least one BCM 210, the PDB 202 may be located anywhere inthe information handling system 200, even external to the chassis 208.In alternate embodiments, the PDB 202 may be located along the back ofthe information handling blade compute module system 200 and may bereferred to as a power distribution back-plane (not shown).

The high density blade compute module system 200 may be coupled to othercomputer components such as keyboards, video displays and pointingdevices (not expressly shown). Typically, the information handlingsystem 200 may include more than one PSU 206 such that a redundant powersource may be provided. The PSU 206 may supply an output, e.g., anelectrical voltage(s) for the at least one BCM 210. Generally, the PSU206 output is coupled through the PDB 202 for distribution to the atleast one BCM 210. The at least one I/O interfaces 284 and 286 may becoupled to various I/O fabrics associated with the BCMs 210 representedby various data transfer communications protocols, e.g., Ethernet, FibreChannel, Infiniband, etc. Thereby allowing the information handlingsystem 200 to communicate through the at least one I/O interfaces 284and 286 to the desired communications protocol(s). Each of the at leastone I/O interfaces 284 and 286 may be coupled to any or all of the BCMs210 over appropriate communications protocol fabrics selected by I/Ofabric daughter cards 264 and/or 268 associated with each of the BCMs210 (see FIG. 2). An I/O fabric router 268 may be located separately,e.g., on the midplane 202, from the BCMs 210, and/or I/O fabric routers(multiple routers not shown in FIG. 2) may be located on each of theBCMs 210 a-210 m.

Referring to FIG. 2, depicted is a schematic block diagram of aninformation handling blade compute module system having electroniccomponents mounted on at least one printed circuit board (PCB)(motherboard not shown) and communicating data and control signalstherebetween over signal buses, according to a specific exampleembodiment of the present disclosure. In one specific exampleembodiment, the information handling blade compute module system is acomputer blade compute module system. The information handling computemodule system, generally referenced by the numeral 200, may comprise oneor more blade compute modules (BCMs) 210 a-210 m. For each of the bladecompute modules (BCMs) 210 a-210 m (for illustrative purposes onlycomponents for BCM 210 a are shown) there may be a processor(s) 211 a, anorth bridge 240 a, which may also be referred to as a memory controllerhub or a memory controller that is coupled to a main system memory 250a, and the blade management controller (BMC) 212 a. The north bridge 240a is coupled to the processor(s) 210 a via the host bus 220 a. The northbridge 240 a is generally considered an application specific chip setthat provides connectivity to various buses, and integrates other systemfunctions such as a memory interface. For example, an Intel 820E and/or815E chip set, available from the Intel Corporation of Santa Clara,Calif., provides at least a portion of the north bridge 240 a. The chipset may also be packaged as an application specific integrated circuit(ASIC). The north bridge 240 a typically includes functionality tocouple the main system memory 250 a to other devices within theinformation handling system 200. Thus, memory controller functions suchas main memory control functions typically reside in the north bridge240 a. In addition, the north bridge 240 a provides bus control tohandle transfers between the host bus 220 a and a second bus(es), e.g.,PCI bus 270 a. A third bus(es) 268 a may also comprise other industrystandard buses or proprietary buses, e.g., ISA, SCSI, 1 ²C, SPI, USB,LPC buses through a south bridge(s) (bus interface) 262 a. The BMC 212 amay be coupled to the blade 210 a with a low pin count (LPC) bus 213 athrough the south bridge 262 a. Each BMC 212 of the blades 210 may becoupled to a service processor 284 in the CMC 204 over, for example butnot limited to, a standard Ethernet link 280. The CMC 204 may controlvarious blade system chassis functions and may be used to communicate(e.g., broadcast firmware updates) to each BMC 212 of the blades 210 inthe blade compute module system 200.

The I/O interfaces 284 and 286 may be common to all of the BCMs 210.These I/O interfaces 284 and 286 may be used for communicating withexternal networks, disk drives, etc., over various communicationsprotocols, e.g., Ethernet, Fibre Channel, Infiniband, etc. Each of theseI/O interfaces 284 and 286 may have fabric busses 294 and 296,respectively, that are unique to the I/O interface types. Each of theBCMs 210 may communicate to desired ones of the I/O interfaces 284and/or 286 with I/O fabric daughter cards 264 a and/or 266 a. The I/Ofabric daughter cards 264 a and/or 266 a may be coupled to the southbridge 262 a data bus 270 a and to the respective ones of the fabricbusses 294 and 296 through a fabric router 268. It is contemplated andwithin the scope of this disclosure that one or more I/O fabric daughtercards, e.g., N, where N is a positive integer number, may be containedon a BCM 210 and one or more I/O fabric interfaces, e.g., N, where N isa positive integer number, may be part of the information handlingsystem 200. The I/O fabric router 268 may be located separately, e.g.,on the midplane 202, from the BCMs 210, and/or there may be a pluralityof I/O fabric routers (multiple routers not shown in FIG. 2) that may belocated on respective ones of the BCMs 210 a-210 m.

Referring now to FIG. 3, depicted is a schematic block diagram of a moredetailed input-output (I/O) fabric topology of the information handlingblade compute module system illustrated in FIG. 2, according to aspecific example embodiment of the present disclosure. The I/O fabricdaughter cards 264 and 266 are coupled to bus 270 of the BCM 210 and tothe fabric router 268. The fabric router 268 couples each of the I/Ofabric daughter cards 264 and 266 to respective ones of the I/Ointerfaces 284 and 286. The BMC 212 may monitor the I/O fabric daughtercards 264 and 266, over information bus 302 to determine the I/O fabrictype of each of the I/O fabric daughter cards 264 and 266. The CMC 204also may monitor the I/O interfaces 284 and 286, over bus 282, todetermine the I/O fabric types thereof.

The CMC 204 and BMC 212 may communicate with each other, over bus 306,so that the BMC 212 may be aware of what I/O interfaces are located onthe busses 294 and 296. Since the BMC 212 knows the I/O fabric type ofeach of the I/O fabric daughter cards 264 and 266, if there is acorresponding I/O interface 284 and/or 286 of the same fabric type thenthe BMC 212 may control the fabric router 268 so as to couple the I/Ofabric daughter cards 264 and 266 to the respective ones of the I/Ointerface 284 and 286. It is contemplated and within the scope of thisdisclosure that one or more I/O fabric daughter cards, e.g., N, where Nis a positive integer number, may be contained on a BCM 210 and that oneor more I/O fabric interfaces, e.g., N, where N is a positive integernumber, may be part of the information handling system 200. Thisconfiguration may be incorporated for each of the BCMs 210, and the I/Ointerface 284 and 286 incorporated into the information handling system200 (see FIG. 1). If there is not a corresponding I/O interface for anI/O fabric daughter card, then the BMC may disable that I/O daughtercard and/or not couple the unpaired I/O fabric daughter from any of thefabric busses 294 and 296.

For example, when the information handling system 200 is started up, theCMC 204 may monitor the fabric types of the I/O interfaces 284 and 286therein (It is contemplated and within the scope of this disclosure thatmore than two I/O interfaces may be present). The I/O fabric daughtercards of each BCM 210 may be monitored with the respective BMC 212. Themonitored information of what I/O interfaces are in the informationhandling system 200 may be sent to each of the BMCs 212 such that eachBMC 212 may control its associated fabric router 268 to couple the I/Ofabric daughter cards 264 and 266 to the appropriate fabric busses foroperation with the appropriate I/O interfaces 284 and 286. Otherwise ifthere no match between an I/O fabric daughter card and an I/O interfacethen the BMC 212 may disable that I/O fabric daughter card and issue anerror message to alert an information system administrator and/ortechnical support.

Alternatively, the BMC 212 may only monitor the type (function) of eachof the respective I/O fabric daughter cards 264 and 266 in theassociated BCM 210, and then each BMC 212 may report the type(s) of I/Ofabric daughter cards 264 and 266 in the respective BCM 210 to the CMC204. When a fabric conflict is detected, the CMC 204 may be able todetermine if the fabric conflict can be resolved by swapping the fabricinterconnections (busses) with the fabric router 268. If a resolution ispossible then the CMC 204 may instruct the respective BMC 212 to causethe fabric router 268 to swap (interchange) the fabric busses 294 and296 between the I/O fabric daughter cards 264 and 266 so as to obtaincorrect fabric matching therebetween. If no resolution is possible, thenthe daughter card fabric interconnection may be disabled and anappropriate alert message may be sent to a user, administrator, etc.

The aforementioned operation may allow a blade to continue to functionif there is an I/O fabric mismatch due to technician or user error.Damage to the information handling system circuits may also be preventeddue to I/O fabric mismatched connections. No longer will the informationhandling system hang-up during a boot because of mismatched I/O fabricdaughter cards and I/O interfaces. According to the teachings of thisspecification, optimized PCI Express bandwidth may be obtained byallocating only those lanes that are being used.

Referring now to FIG. 4, depicted is a flow diagram of a sequence ofsteps for checking input-output (I/O) fabric topology in a blade computemodule system and for taking corrective action when an I/O fabrictopology conflict exists, according to a specific example embodiment ofthe present disclosure. In Step 402 of FIG. 4, a user initiates apower-up of a blade compute module system. In step 404 detection of thedaughter card and I/O interface module fabrics are determined. In step406, a determination is made whether a fabric conflict exists. If nofabric conflict exists, then in step 408 a power-up confirmation is sentto the BMC. In step 410 the appropriate daughter cards are enabled andthen in step 418 the boot-up of the blade compute module systemcontinues. If there is a fabric conflict, then in step 414 adetermination is made whether the conflict may be resolved by swappingdaughter card fabric connections to the appropriate I/O interfacemodules in step 416. Then going to step 418 for continuing boot-up ofthe blade compute module system. If the conflict cannot be resolved thenin step 420 a power-up denial is sent to the respective BMC, and in step422 that blade I/O fabric may be disabled and an unresolved fabricconflict alert is sent to a user and/or systems administrator.

While embodiments of this disclosure have been depicted, described, andare defined by reference to example embodiments of the disclosure, suchreferences do not imply a limitation on the disclosure, and no suchlimitation is to be inferred. The subject matter disclosed is capable ofconsiderable modification, alteration, and equivalents in form andfunction, as will occur to those ordinarily skilled in the pertinent artand having the benefit of this disclosure. The depicted and describedembodiments of this disclosure are examples only, and are not exhaustiveof the scope of the disclosure.

What is claimed is:
 1. An information handling system havinginput-output fabric conflict detection and resolution, said systemcomprising: a chassis management controller; at least one input-output(I/O) interface, wherein each of the at least one I/O interface has onefirst I/O fabric type; an I/O fabric router; and at least one bladecompute module having at least one I/O daughter card, and a blademanagement controller, wherein each of the at least one I/O daughtercard has one second I/O fabric type; wherein: the at least one I/Odaughter card is coupled to the I/O fabric router, the I/O fabric routeris coupled to the at least one I/O interface, the blade managementcontroller is coupled to the at least one I/O daughter card, the I/Ofabric router, and the chassis management controller; and the chassismanagement controller is coupled to the at least one I/O interface;whereby: the blade management controller is configured to determine thesecond I/O fabric type of each of the at least one I/O daughter card andreport the second I/O fabric type of each of the at least one I/Odaughter card to the chassis management controller; the chassismanagement controller is configured to determine whether the first I/Ofabric type of each of the at least one I/O interface matches the secondI/O fabric type of each of the at least one I/O daughter card; if thesecond I/O fabric type of at least one of the at least one I/O daughtercard matches the first I/O fabric type of at least one of the at leastone I/O interface, then the information handling system is configured toboot up and the chassis management controller is configured to instructthe blade management controller to change I/O fabric routing for thematching at least one of the at least one I/O daughter card and at leastone of the at least one I/O interface through the I/O fabric router; andif no first I/O fabric type of at least one of the at least one I/Ointerface matches the second fabric type of the at least one I/Odaughter card, then the chassis management controller is configured todisable the at least one I/O daughter card.
 2. The information handlingsystem according to claim 1, wherein the at least one I/O interface isselected from the group consisting of an Ethernet I/O interface, a FibreChannel I/O interface, and an Infiniband I/O interface.
 3. Theinformation handling system according to claim 1, wherein the at leastone I/O daughter card plugs into a card connector on the at least oneblade compute module.
 4. The information handling system according toclaim 1, wherein the at least one I/O daughter card is a plurality ofI/O daughter cards.
 5. The information handling system according toclaim 4, wherein the plurality of I/O daughter cards comprises Ndaughter cards, where N is a positive integer value.
 6. The informationhandling system according to claim 4, wherein the at least one I/Ointerface is a plurality of I/O interfaces.
 7. The information handlingsystem according to claim 6, wherein the plurality of I/O interfaces andthe plurality of I/O daughter cards have corresponding I/O fabrics. 8.An information handling system having input-output fabric conflictdetection and resolution, said system comprising: a chassis managementcontroller; at least one input-output (I/O) interface, wherein each ofthe at least one I/O interface has one first I/O fabric type; an I/Ofabric router; and at least one blade compute module having at least oneI/O daughter card, and a blade management controller, wherein each ofthe at least one I/O daughter card has one second I/O fabric type;wherein: the at least one I/O daughter card is coupled to the I/O fabricrouter; the I/O fabric router is coupled to the at least one I/Ointerface fabric; the blade management controller is coupled to the atleast one I/O daughter card, the I/O fabric router, and the chassismanagement controller; and the chassis management controller is coupledto the at least one I/O interface; whereby: the chassis managementcontroller is configured to determine the first I/O fabric type of eachof the at least one I/O interface and report the first I/O fabric typeof each of the at least one I/O interface to the blade managementcontroller; the blade management controller is configured to determinethe second I/O fabric type of each of the at least one I/O daughter cardand determine whether the first I/O fabric type of at least one of theat least one I/O interface matches the second I/O fabric type of the atleast one I/O daughter card ; if the first I/O fabric type of at leastone of the at least one I/O interface and the second I/O fabric type ofthe at least one I/O daughter card matches, then the informationhandling system is configured to boot up and the blade managementcontroller is configured to change I/O fabric routing for the matchingat least one of the at least one I/O interface fabric and the at leastone I/O daughter card through the I/O fabric router; and if the secondI/O fabric type of the at least one I/O daughter card does not match thefirst I/O fabric type of at least one I/O interface, then the blademanagement controller is configured to disable the at least one I/Odaughter card.
 9. The information handling system according to claim 8,wherein the at least one I/O interface is selected from the groupconsisting of an Ethernet I/O interface, a Fibre Channel I/O interface,and an Infiniband I/O interface.
 10. The information handling systemaccording to claim 8, wherein the at least one I/O daughter card plugsinto a card connector on the at least one blade compute module.
 11. Theinformation handling system according to claim 8, wherein the at leastone I/O daughter card is a plurality of I/O daughter cards.
 12. Theinformation handling system according to claim 11, wherein the pluralityof I/O daughter cards comprises N daughter cards, where N is a positiveinteger value.
 13. The information handling system according to claim11, wherein the at least one I/O interface is a plurality of I/Ointerfaces.
 14. The information handling system according to claim 13,wherein the plurality of I/O interfaces and the plurality of I/Odaughter cards have corresponding I/O fabrics.
 15. A method fordetecting input-output fabric conflicts and resolving any detectedfabric conflicts in an information handling system, said methodcomprising the steps of: determining input-output (I/O) fabric types ofa plurality of I/O interfaces in an information handling system, whereineach of the plurality of I/O interfaces has one I/O fabric type;determining I/O fabric types of a plurality of I/O daughter cardsassociated with a plurality of blade compute modules, wherein each ofthe plurality of I/O daughter cards has one I/O fabric type; couplingeach I/O fabric type of the plurality of I/O daughter cards to anassociated one of the plurality of I/O interfaces having the same I/Ofabric type, wherein the step of coupling comprises changing I/O fabricrouting of the plurality of I/O daughter cards through an I/O fabricrouter so that at least one of the I/O fabric types of the plurality ofI/O interfaces and the plurality of I/O daughter cards match; decouplingany one of the I/O daughter cards having an I/O fabric type not found inany one of the plurality of I/O interfaces, and disabling the one of theplurality of blade compute modules having the I/O daughter card with anI/O fabric type not found in any one of the plurality of I/O interfaces.16. The method according to claim 15, further comprising the steps of:sending a power-up denial to a one of the plurality of blade computemodules having the I/O daughter card with the I/O fabric type not foundin any of the plurality of I/O interfaces, and sending a fabric conflictalert.
 17. The method according to claim 15, further comprising the stepof booting up all of the plurality of blade compute modules having noI/O fabric conflicts.
 18. A method for detecting input-output fabricconflicts and resolving any detected fabric conflicts in an informationhandling system, said method comprising the steps of: initiatingpower-up of an information handling system comprising a plurality ofblade compute modules and a plurality of input-output (I/O) interfaces;detecting I/O fabric types of a plurality of I/O daughter cardsassociated with the plurality of blade compute modules, wherein each ofthe plurality of I/O daughter cards has one I/O fabric type; detectingI/O fabric types of the plurality of I/O interfaces, wherein each of theplurality of I/O interfaces has one I/O fabric type; determining whetherthere are any I/O fabric conflicts with how the I/O fabrics of theplurality of I/O daughter cards are coupled to the I/O fabrics of theplurality of I/O interfaces, wherein if there are no I/O fabricconflicts then sending a power-up confirmation to a blade managementcontroller of each of the plurality of blade compute modules, enablingeach of the I/O daughter cards, and continuing booting up theinformation handling system; if there is an I/O fabric conflict thendetermining if the I/O fabric conflict can be resolved, if the I/Ofabric conflict can be resolved then swapping fabric connections throughan I/O fabric router to resolve the I/O fabric conflict, and if the I/Ofabric conflict cannot be resolved then sending a power-up denial to theblade management controller of the one of the plurality of blade computemodules having the I/O fabric conflict and disabling the one of theplurality of blade compute modules having the I/O fabric conflict. 19.The method according to claim 18, further comprising the step of sendingan I/O fabric conflict alert when the I/O fabric conflict occurs. 20.The information handling system according to claim 1, wherein the I/Ofabric router is part of the at least one blade compute module.
 21. Theinformation handling system according to claim 1, wherein the I/O fabricrouter is separate from the at least one blade compute module.
 22. Theinformation handling system according to claim 8, wherein each at leastone blade compute module has an I/O fabric router.
 23. The informationhandling system according to claim 8, wherein the at least one bladecompute module is separate from the I/O fabric router.